Repository navigation
Add the Touch ID review lessons to AGENTS.md and CONTRIBUTING.md - #14
Conversation
Reviews of the Touch ID branches kept finding the same kinds of slip: a test that passed only because the Mac running it had Omarchy installed, a detection path that could hide the one before it, an integration test that skipped silently in CI, a green run that never reached the code, a udev add rule that missed the upgrade installing it, and a once-only invitation that could fire before its dependencies shipped. AGENTS.md now says so. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
|
@scottjones good idea to write these down; lines 26 and 28 are precise and fit the file. A few wording fixes so agents don't over-apply them:
|
Wording from Marcelo's review, so agents don't over-apply them: the hook rule covers only an add that must reach a device already present, and the hook never fails the transaction; the once-only rule is about invitations, not first boot; tests may read /sys fixtures, never the host's; and the pin rule doesn't touch the skip when OMARCHY_TEST_RUNTIME is unset. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
|
@maralcbr thanks, applied all four in |
|
Thanks @scottjones, the rules capture real lessons from the Touch ID work. One change before merge:
Smaller things:
With the line 25 fix in, this is good to merge from my side. |
Marcelo noted "invitation" is defined nowhere else in the repo, so an agent could not act on the rule. It now names the one-time post-update fingerprint setup offer and the change that triggers it, a new entry in fingerprint-readers. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
|
Thanks @scottjones, the line 25 fix and the invitation definition are in. A few things left, all wording or timing:
Line 21 is also a release gate not written down in |
From Marcelo's review: the invitation rule now says where its names come from (omarchy-hw-fingerprint, the runtime's detector, reads fingerprint-readers, the platform file omarchy-mac ships in #12), and "published" means published to the repositories Macs update from. systemd-analyze verify --root applies where the container can verify units, at whatever tree is staged. The runtime pin moves to a commit that has what a test needs, not the exact commit that added it. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…ONTRIBUTING.md AGENTS.md said #12 brought both the platform file and the detector that reads it. #12 adds fingerprint-readers; omacom/omarchy#14675 teaches the runtime's omarchy-hw-fingerprint to read it. CONTRIBUTING.md now states the release rule for one-time prompts beside the cold-boot evidence rule, so merging the AGENTS.md rule doesn't make policy the contributor guide leaves out. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
|
@maralcbr thanks for this, and sorry for the slow reply. All five are in:
Could you take another look when you get a minute? It still needs an approval before it can merge. |
maralcbr
left a comment
There was a problem hiding this comment.
Thanks @scottjones, all of it is in: the source of the fingerprint names, "published to the repositories Macs update from", the conditional --root, "a commit that has it", and the refreshed description. Good to merge from my side.
- Nit, line 21: the last sentence reads as true today, but
fingerprint-readersonly arrives with #12, and the pinnedomarchy-hw-fingerprintdoesn't read it until omacom/omarchy#14675 lands. Either merge this after #12, or something like "#12 addsfingerprint-readersto omarchy-mac, and omacom/omarchy#14675 teaches the runtime's detector,omarchy-hw-fingerprint, to read it."
Summary
Adds two rules and a Tests section to
AGENTS.md, from what the Touch ID reviews (#12, omacom/omarchy-mac#694, omacom/omarchy-pkgs#806) kept catching, and states the invitation rule inCONTRIBUTING.md.Rules:
addthat must reach a device already present also gets a pacman hook, which exits 0 in a chroot or an unbooted root and never fails the transaction. Anaddthat should only run when the device appears doesn't.fingerprint-readersplatform file, and Find fingerprint readers a platform names omarchy#14675 makes the runtime's detector read it.Tests:
omarchy-*commands,/sysor running services, and it stubs external dependencies while keeping the real commands under test. Where the container can verify units, it runssystemd-analyze verifywith--rootat the staged tree.test/integration/runtimeto a commit that has it instead of skipping.Evidence
Documentation only.
check-scope,check-architecture-gatesandcheck-fixture-driftpass.Merge Danger
Door: two-way
Merging makes the invitation rule release policy.
CONTRIBUTING.mdnow states it under Pull requests, next to the cold-boot evidence rule.Blast Radius: docs
🤖 Generated with Claude Code